Child rider features for an autonomous vehicle

ABSTRACT

An autonomous vehicle including a vehicle propulsion system, a braking system, a steering system, and a computing system that is in communication with the vehicle propulsion system, the brake system, and the steering system. The computing system can receive an indication an account associated with a passenger of the autonomous vehicle for a trip of the autonomous vehicle includes a predefined parent-child link with a second account. The predefined parent-child link indicates the account associated with the passenger is subordinate to the second account and a parent-child relationship exists between the passenger and a person associated with the second account. Responsive to receiving the indication of the parent-child link and the passenger being the child in the parent-child relationship, the computing system can control the autonomous vehicle to enable a linked account feature that would otherwise be disabled.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional application of U.S. patent applicationSer. No. 16/836,865, filed Mar. 31, 2020, and entitled “CHILD RIDERFEATURES FOR AN AUTONOMOUS VEHICLE”, which is a continuation of U.S.Pat. No. 10,640,082, filed on Feb. 11, 2019, and entitled “CHILD RIDERFEATURES FOR AN AUTONOMOUS VEHICLE”, the entireties of which areincorporated herein by reference.

BACKGROUND

An autonomous vehicle is a motorized vehicle that can operate without ahuman driver. According to an exemplary scenario, a passenger mayrequest a ride in an autonomous vehicle from a given location to adestination location. When the passenger requests the ride in theautonomous vehicle, he or she may be provided with informationconcerning the upcoming ride prior to pickup (e.g., pickup time, pickuplocation, information to identify the autonomous vehicle). Moreover, theautonomous vehicle may pick up the passenger at the given location andfollow a route to the destination location, where the passenger can bedropped off.

In conventional approaches, substantially similar types of informationmay be provided responsive to requesting a ride in an autonomous vehicleregardless whether a passenger is an adult or a child. Moreover, theautonomous vehicle may use substantially similar operating proceduresregardless whether the passenger is an adult or a child.

SUMMARY

The following is a brief summary of subject matter that is described ingreater detail herein. This summary is not intended to be limiting as toscope of the claims.

Described herein are various technologies pertaining to controllingoperation of an autonomous vehicle based on a passenger of theautonomous vehicle being a child. For instance, a particular passengercan be identified as being a child passenger based on having aparent-child link in their account. With more specificity, theautonomous vehicle can receive an indication of the parent-child link inan account of a child passenger and can enable a linked account featureof the autonomous vehicle based on the presence of the parent-childlink. But for the presence of the parent-child link the linked accountfeature would be disabled. The linked account feature enabled can dependon an identity(s) of the passenger(s). For instance, a first linkedaccount feature can be enabled when the child is traveling alone and asecond linked account feature can be enabled when the parent istraveling with their child.

In one example, an autonomous vehicle includes a vehicle propulsionsystem, a braking system, a steering system, and a computing system thatis in communication with the vehicle propulsion system, the brakingsystem, and the steering system. The computing system can receive anindication that an account of a passenger of the autonomous vehicle fora trip of the autonomous vehicle includes a predefined parent-child linkwith a second account. The predefined parent-child link can indicate aparent-child relationship between the passenger and a person associatedwith the second account. In one embodiment, the passenger is the childin the parent-child relationship. Responsive to receiving the indicationof the parent-child link, the computing system can enable a linkedaccount feature of the autonomous vehicle.

In an embodiment, the linked account feature includes controllingoperation of the autonomous vehicle to perform certain actions thatwould not be performed otherwise. For instance, doors of the autonomousvehicle can be individually unlocked based on a position of the childpassenger compared to a position of the parent passenger. In anotherembodiment, the linked account feature includes displaying notificationson a mobile device operated by the parent of the parent-child link thatwould not otherwise be displayed.

The above-described technologies present various advantages overconventional approaches to autonomous vehicle operation. First, unlikethe conventional approach of applying a similar operation for a varietyof passengers regardless whether the passengers are adults or children,the above-described technologies enable selective operation of anautonomous vehicle based on a passenger's account being subordinate toanother person's account. Secondly, the above-described system allows aparent to control operation of an autonomous vehicle their child isriding in by making changes to the child's account.

The above summary presents a simplified summary in order to provide abasic understanding of some aspects of the systems and/or methodsdiscussed herein. This summary is not an extensive overview of thesystems and/or methods discussed herein. It is not intended to identifykey/critical elements or to delineate the scope of such systems and/ormethods. Its sole purpose is to present some concepts in a simplifiedform as a prelude to the more detailed description that is presentedlater.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary autonomous vehicle.

FIG. 2 illustrates another exemplary autonomous vehicle.

FIG. 3 illustrates a further exemplary autonomous vehicle.

FIG. 4 illustrates an exemplary autonomous vehicle in communication witha computing system.

FIG. 5 illustrates another exemplary autonomous vehicle in communicationwith a computing system.

FIG. 6 illustrates an exemplary autonomous vehicle in communication witha mobile computing device.

FIG. 7 illustrates an exemplary computing system in communication withan autonomous vehicle and a mobile computing device.

FIG. 8 is a flow diagram that illustrates an exemplary methodologyexecuted by an autonomous vehicle for controlling operation of theautonomous vehicle based on a parent-child link.

FIG. 9 illustrates an exemplary computing system.

DETAILED DESCRIPTION

Various technologies pertaining to selecting are now described withreference to the drawings, wherein like reference numerals are used torefer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of one or more aspects. It maybe evident, however, that such aspect(s) may be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form in order to facilitate describing one ormore aspects. Further, it is to be understood that functionality that isdescribed as being carried out by certain system components may beperformed by multiple components. Similarly, for instance, a componentmay be configured to perform functionality that is described as beingcarried out by multiple components

Moreover, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

Further, as used herein, the terms “component” and “system” are intendedto encompass computer-readable data storage that is configured withcomputer-executable instructions that cause certain functionality to beperformed when executed by a processor. The computer-executableinstructions may include a routine, a function, or the like. It is alsoto be understood that a component or system may be localized on a singledevice or distributed across several devices. Further, as used herein,the term “exemplary” is intended to mean serving as an illustration orexample of something and is not intended to indicate a preference.

Moreover, as used herein “parent” is intended to encompass any partythat has been entrusted to care for a child. The party can include, butis not limited to, a biological or adoptive mother, a biological oradoptive father, a grandmother and/or grandfather, a state-mandatedguardian, and/or the like. Further, as used herein “child” is intendedto encompass a minor or someone legally incapable of managing his or herown affairs.

Disclosed are various technologies that permit a parent to modifyoperation of an autonomous vehicle their child is riding in. An accountassociated with the child can include a parent-child link making thechild's account subordinate to an account associated with the parent.This parent-child link can allow the parent to make certainmodifications to the child's account that the child may not be able toalter. For instance, the parent can specify that the child has toindicate that they feel secure in the autonomous vehicle before theautonomous vehicle can begin the trip. The existence of the parent-childlink in the child's account causes the autonomous vehicle to enablecertain linked account features which will be described in detail below.Absent the parent-child link the linked account features are disabled.If the parent rides without the child and/or an account associated withthe passenger doesn't include a parent-child link, the autonomousvehicle will not enable the linked account feature. Thus, a parent canmodify operation of the autonomous vehicle by establishing theparent-child link.

With reference now to FIG. 1, illustrated is an exemplary autonomousvehicle 100. The autonomous vehicle 100 can navigate about roadwayswithout human conduction based upon sensor signals output by sensorsystems of the autonomous vehicle 100. The autonomous vehicle 100includes a plurality of sensor systems, namely, a sensor system 1 102, .. . , and a sensor system N 104 (collectively referred to herein assensor systems 102 and 104). The sensor systems 102 and 104 are ofdifferent types and may be arranged about the autonomous vehicle 100.For example, the sensor system 1 102 may be a lidar sensor system andthe sensor system N 104 may be a camera (image) system. Other exemplarysensor systems 102 and 104 included are radar sensor systems, GPS sensorsystems, sonar sensor systems, infrared sensor systems, and the like.

The autonomous vehicle 100 further includes several mechanical systemsthat are used to effectuate appropriate motion of the autonomous vehicle100. For instance, the mechanical systems can include, but are notlimited to, a vehicle propulsion system 108, a braking system 110, and asteering system 112. The vehicle propulsion system 108 may be anelectric motor, an internal combustion engine, or the like. The brakingsystem 110 can include an engine brake, brake pads, actuators, and/orany other suitable componentry that is configured to assist indecelerating the autonomous vehicle 100. The steering system 112includes suitable componentry that is configured to control thedirection of the movement of the autonomous vehicle 100.

The autonomous vehicle 100 additionally comprises a computing system 114that is in communication with the sensor systems 102 and 104, thevehicle propulsion system 108, the braking system 110, and/or thesteering system 112. The computing system 114 includes a processor 116and memory 118 that includes computer-executable instructions that areexecuted by the processor 116. In an example, the processor 116 can beor include a graphics processing unit (GPU), a plurality of GPUs, acentral processing unit (CPU), a plurality of CPUs, anapplication-specific integrated circuit (ASIC), a microcontroller, orthe like.

The memory 118 includes a control system 122 configured to controloperation of the vehicle propulsion system 108, the braking system 110,and/or the steering system 112. The memory 118 further includes a linkedaccount system 120 that causes the autonomous vehicle 100 to enable alinked account feature in response to receiving an indication an accountof a passenger includes a parent-child link, as will be described indetail below.

In order to receive the indication, the autonomous vehicle 100 mayfurther include a transceiver 106. The transceiver 106 is configured totransmit data from the autonomous vehicle 100 and/or receive data at theautonomous vehicle 100. Thus, the autonomous vehicle 100 can be incommunication with one or more computing systems.

The linked account system 120 is configured to enable one or more linkedaccount feature in response to the linked account system 120 receivingan indication a link exists between at least two accounts. Morespecifically, an indication that an account corresponding to a passengerof the autonomous vehicle 100 includes a predefined parent-child link toa second account. The parent-child link can indicate a parent-childrelationship between the passenger and a party associated with thesecond account. For instance, the passenger is the child and the partyassociated with the second account is his or her parent. In anotherexample, the passenger is the parent and the party associated with thesecond account is his or her child.

In one embodiment, the linked account system 120 is configured todetermine whether the parent-child link exists in the account associatedwith the passenger. The linked account system 120 can be configured toaccess a data store which stores the account associated with thepassenger to determine whether the parent-child exists in the account.In another embodiment, a separate computing system includes a data storewhich stores the account associated with the passenger and the computingsystem transmits data to the autonomous vehicle indicative of theaccount associated with the passenger having the parent-child link.

The parent-child link can further indicate that one of the accounts isat least partially subordinate to the other account. For instance, theparent account 408 (FIG. 4) can control certain settings for and/orinformation in the child account 410 (FIG. 4), as will be described indetail below. The parent-child link may further prevent the child fromadjusting the settings and/or information supplied by the parent.

Responsive to receiving indication of the parent-child link, the linkedaccount system 120 enables one or more linked account features. Theamount and kind of linked account feature can depend on who in theparent-child relationship is a passenger in the autonomous vehicle 100.Additionally, the parent in the parent-child link can predefine in thechild account which linked account features to enable. For instance, afirst linked account feature is enabled when the child is the passenger.In another example, a second linked account feature is enabled when theparent and the child are both passengers.

In one embodiment, the linked account system 120 can be furtherconfigured to enabled one or more linked account features only when thepassenger(s) in the autonomous vehicle 100 includes the child. Forinstance, when the parent rides in the autonomous vehicle 100 withoutthe child(s), the linked account system 120 may not enable a linkedaccount feature.

Various exemplary linked account features are now described; one of moreof the exemplary linked account features can be enabled simultaneouslyand/or separately. The illustrated linked account features examples canfurther be enabled at different times throughout the trip of the childpassenger and/or the parent passenger. Further, different linked accountfeatures may be enabled when the child is the sole passenger and whenthe parent and the child are taking a trip together.

In an example, the linked account feature may include providing a childpassenger additional time to get settled in the autonomous vehicle 100before the autonomous vehicle 100 begins a trip of the child passengerin the autonomous vehicle 100. For instance, the linked account featurecan include providing additional time for a child passenger to getsituated in the autonomous vehicle 100 before beginning a trip in theautonomous vehicle 100. The time provided for the child passenger to getsituated can be in addition to time provided to a passenger who does nothave a parent-child link in their account to get situated in theautonomous vehicle 100. The linked account system 120 can be configuredto cause the control system 122 to control at least one of the vehiclepropulsion system 108, the braking system 110, or the steering system112 to cause the autonomous vehicle 100 to remain stationary for a setperiod of time.

The period of time can be predefined for a child passenger by a parentand/or can be set by a third party that could be universal for aplurality of child passengers. For instance, a period of time can bedefined by the parent in an account corresponding to the child passengerprior to requesting a trip for the child passenger in the autonomousvehicle 100. The period of time can depend on a characteristic(s) of thechild passenger, a characteristic(s) of the autonomous vehicle 100,and/or a characteristic(s) of the trip. A characteristic of the childpassenger can include the age of the child passenger, cognitive abilityof the child passenger, and/or the like. A characteristic of theautonomous vehicle 100 can include arrangement of seats within theautonomous vehicle 100. A characteristic of the trip can include adistance of a child passenger from an anticipated pick-up location, adistance from an anticipated drop-off location to a destination of thetrip, whether the parent is traveling with the child passenger, and/orthe like.

In another example, the linked account feature can include limiting whatinformation is displayed on a user interface device operated by a parentpassenger versus one operated by a child passenger. Conventionally, eachuser interface device in an autonomous vehicle 100 is configured topresent a similar interface to for all users (i.e. passengers). Theinterface can comprise a control interface that presents access tocontrols of the autonomous vehicle 100. The controls can includestarting a trip, ending a trip, locking and/or unlocking doors of theautonomous vehicle 100, requesting support, and/or the like.

The disclosed linked account system 120 can be configured to limit whichuser interface device presents the control interface and/or to changewhat is displayed by a user interface device operated by a childpassenger. For instance, the linked account feature can includepresenting a control interface to a parent passenger and presenting adifferent interface to a child passenger. In another example, the parentcan select what is displayed on a user interface device operated by thechild passenger.

As illustrated in FIG. 2, the autonomous vehicle 100 can include aplurality of user interface devices configured for use by a passenger ora plurality of passengers of the autonomous vehicle 100, namely, a userinterface device 1 202, . . . , and a user interface device M 204(collectively referred to herein as user interface devices 202 and 204).The user interface devices 202 and 204 can be arranged about theautonomous vehicle 100 and may be arranged to allow each passenger tointeract with a separate user interface device. Each user interfacedevice includes a display 206, whereupon graphical features may bepresented. For instance, a graphical user interface (GUI) may bepresented as part of the graphical features.

In an illustrative example, the linked account system 120 can includedisplay component 200 configured to require a passenger to enter a codeinto a user interface device before the user interface device presentsthe autonomous vehicle 100 controls. The code can comprise any suitablecombination for security, such as a four-digit pin or a password. Thedisplay component 200 can be further configured to prevent a second(e.g., child) passenger from entering a code into a second userinterface device once a parent passenger has entered a code into a userinterface device. Thus, by entering the code into a user interfacedevice, a parent passenger can prevent a child passenger fromaccidentally or intentionally causing a second user interface device topresent the control interface. Once the parent passenger enters the codeinto a user interface device in an autonomous vehicle 100, the displaycomponent 200 can additionally be configured to cause the other userinterface devices in the autonomous vehicle 100 s to present informationother than control interface information.

The parent can also cause a user interface device operated by the childpassenger to present child-focused content to the child passenger. Morespecifically, the display component 200 can be further configured topresent, via a user interface device, child content designed for a childpassenger. The child content can include games, learning modules, and/orchildren-appropriate videos that a child passenger can watch during atrip of the autonomous vehicle 100. The parent may select in advancewhat child content is presented to the child passenger or the displaycomponent 200 may select what child content is presented based on acharacteristic(s) of the child passenger (e.g., age, gender, previouschild content, etc.).

In an embodiment, a parent can indicate that a child passenger is ridingin a specific seat of the autonomous vehicle 100 during a trip of theautonomous vehicle 100; the display component 200 can then cause a userinterface device associated with that specific seat to present the childcontent. In this embodiment, the parent need not be in the autonomousvehicle 100 and can remotely determine and indicate to the displaycomponent 200 what seat the child passenger is riding in.

In another embodiment, a parent passenger in an autonomous vehicle 100can indicate, via a user interface device operated by the parentpassenger, which seat of the autonomous vehicle 100 a child passenger isin and/or which user interface device is operated by a child passenger.In yet another embodiment, the display component 200 can be configuredto detect a location of a child passenger within the autonomous vehicle100 and to cause a user interface device associated with that locationto present the child content.

In addition to the control interface, the parent can be provided withchild passenger-centric specifications about the autonomous vehicle 100and/or guide(s) for securing a child passenger in the autonomous vehicle100. The display component 200 can be configured to cause a userinterface device operated by a parent passenger to display childpassenger-centric specifications for the autonomous vehicle 100. Forinstance, the child passenger-centric specifications can include numberof seats in the autonomous vehicle 100, available space in theautonomous vehicle 100 to store passenger items (e.g., stroller,child-care bag, etc.), devices for securing a child passenger during atrip of the autonomous vehicle 100 (e.g., seat belts, car seats, etc.),and/or the like.

In another example, the display component 200 can be configured to causea user interface device operated by a parent passenger to display aguide or guides for securing the child passenger in the autonomousvehicle 100. For example, the guide can include steps for installing andsecuring a car seat, whether provided with the autonomous vehicle 100 orbrought by the parent. The guide can also inform a parent with how tomove interior parts of the autonomous vehicle 100, if necessary, tostore a stroller or a bag.

In another example, the linked account feature can comprise selectivelylocking and unlocking doors and/or windows of the autonomous vehicle 100based on a position of a parent passenger and/or a child passenger. Forinstance, the autonomous vehicle 100 can be configured to automaticallyunlock the door associated with a parent passenger and leave theremaining doors locked when the autonomous vehicle 100 reaches adrop-off location. In another example, the autonomous vehicle 100 canrequire a passenger to enter a specific prompt to unlock one or more ofthe doors of the autonomous vehicle 100 to prevent a child passengerfrom accidentally unlocking a door.

In an embodiment, the autonomous vehicle 100 can include one or moredoor locks and/or one or more window locks. As illustrated in FIG. 3,the autonomous vehicle 100 can include a door lock 1 302, . . . , and adoor lock M 304 (collectively referred to herein as door locks 302 and304) and a window lock 1 306, . . . , and a window lock X 308(collectively referred to herein as window locks 306 and 308). The doorlocks 302 and 304 and the window locks 306 and 308 can each beselectively movable between a locked position and an unlocked position.The linked account system 120 can include a locking component 300 thatcan be configured to selectively lock and/or unlock parts of theautonomous vehicle 100. More particularly, the locking component 300 canbe configured to separately and/or simultaneously lock and/or unlock oneor more of the door locks 302 and 304. Similarly, the locking component300 can be further configured to separately and/or simultaneously lockand/or unlock one or more of the window locks 306 and 308.

In an embodiment, the locking component 300 can be configured to placeall the door locks 302 and 304 in the locked position while theautonomous vehicle 100 is traveling between a pick-up location and adrop-off location for a trip of a passenger in the autonomous vehicle100. The locking component 300 can further be configured to unlock oneor more of the door locks 302 and 304 at the pick-up location and/ordrop-off location.

In one example, the locking component 300 is configured to only unlockthe door lock nearest a location of a parent passenger in the autonomousvehicle 100 at the drop-off location when the parent passenger travelswith a child passenger. The location of the parent passenger can bedetermined by any suitable method. For instance, the location of theparent passenger can be determined by a camera. The autonomous vehicle100 can further include an in-cabin camera 310 that is configured tomonitor an interior of the autonomous vehicle 100. The in-cabin camera310 can view the entire interior of the autonomous vehicle 100 and/orcan focus on a specific passenger of the autonomous vehicle 100. Thelocking component 300 can receive information generated by the in-cabincamera 310 and unlock one or more of the door locks 302 and 304 based onthis information. In another example, the location of the parentpassenger can be determined based on which user interface device (FIG.2) the parent passenger is using.

Subsequent to reaching the drop-off location and unlocking the door locknearest the parent passenger, the parent passenger can unlock one ormore of the other door locks 302 and 304. The parent passenger canunlock another door lock via a manual switch within the autonomousvehicle 100 and/or via a prompt displayed by the user interface deviceused by the parent passenger. Thus, the locking component 300 canprevent a child passenger from accidentally or intentionally opening adoor of the autonomous vehicle 100 without approval from the parentpassenger.

The locking component 300 can be further configured to unlock one ormore of the door locks 302 and 304 when a passenger (e.g., childpassenger, parent passenger) indicates a desire to prematurely end theride in the autonomous vehicle 100 by interacting with an end rideinterface. The end ride interface can include a mechanical button withinthe autonomous vehicle 100 and/or a widget displayed on a user interfacedevice operated by the passenger. Responsive to a passenger activatingthe end ride interface, the locking component 300 can unlock one or moreof the door locks 302 and 304 once the autonomous vehicle 100 has haltedmovement.

In an embodiment, the linked account feature comprises presenting a signinforming parties outside the autonomous vehicle 100 that a childpassenger is in the autonomous vehicle 100. For instance, the linkedaccount system 120 can active a physical sign in or on the autonomousvehicle 100 with a phrase configured to inform the parties (e.g., “Babyon Board”). The sign can be digital (e.g., light emitting diode (LED)),physical, and/or the like.

Due to the child account 410 being subordinate to the parent account 408through the parent-child link, the parent can set restrictions on whatthe child can modify in the child account 410 and/or predefine someparameters in the child account 410 that the child does not havepermission to modify. For example, the parent can restrict whatdestinations the child can set for a trip in the autonomous vehicle 100and/or the amount of money the child can spend on trips in theautonomous vehicle 100.

The parent can further indicate one or more requirements to be fulfilledby the child passenger and/or the autonomous vehicle 100 before a tripof the child passenger in the autonomous vehicle 100. The requirementscan include non-pooled trips in the autonomous vehicle 100 for the childpassenger, autonomous vehicle 100 is reasonably free of airborneallergens, the child passenger indicating (e.g. vocally, via a userinterface device) they feel secured in the autonomous vehicle aftersecuring a safety device (e.g., seat belt, car seat) before theautonomous vehicle 100 begins the trip, at least one door of theautonomous vehicle 100 is locked before the autonomous vehicle 100begins the trip, and/or the like.

In the following examples, the linked account feature comprisescontrolling the autonomous vehicle 100 based on one or more of theparameters defined by the parent and/or restrictions in the childaccount 410.

For instance, the parent can predefine one or more locations in thechild account 410. A predefined location included in the child account410 can be an address, a name of a place, geographic coordinates, or thelike. The predefined location can be defined by the parent in the childaccount 410 prior to receipt of a request for a trip for the childpassenger. Due to the parent-child link making the child account 410subordinate to the parent account 408, the child may not be able tochange the predefined location either accidentally or intentionally.

In another example, the parent can indicate in the child account 410that a third party is authorized to request a ride for the child. Theparent can restrict what location the third party may set as the pickuplocation. The parent may further specify that a request from the thirdparty for a trip of the child passenger automatically sets a predefinedlocation as the pickup location (e.g., without the request from thethird party specifying the pickup location). For instance, the parentcan specify in the account of their child that the child is to be pickedup at a local Boys and Girls club, for at least one trip in theautonomous vehicle 100. Since the parent may not know exactly when thechild will be done at the club, the parent can further indicate that theBoys and Girls club and/or a representative thereof can request a ridefor their child from the Boys and Girls club when the child is done atthe club. The parent can further indicate what times the third party canrequest a ride for the child.

In yet another example, the parent can, via the parent-child link,indicate in the child account 410 what funds are available for trips ofthe child passenger. The child account 410 can include a source of funds(e.g., credit card, debit card, bank account) that can be used to payfor one or more trips in an autonomous vehicle 100. The parent cancontrol the type and/or amount of funds that are available. In oneembodiment, the available funds can be used for any type of trip. Inanother embodiment, the parent can indicate certain types of trips theavailable funds can be used on.

In a further example, the parent can set certain authorized times in thechild account 410 when the child or an authorized third party ispermitted to request a trip in an autonomous vehicle 100.

Turning now to FIGS. 4 and 5, in an embodiment, the autonomous vehicle100 can be in communication with a computing system 402 via thetransceiver 106 in the autonomous vehicle 100. The computing system 402can similarly include a transceiver 412. The transceiver 412 isconfigured to transmit data from the computing system 402 and/or receivedata at the computing. Thus, the computing system 402 can be incommunication with the autonomous vehicle 100 and vice versa.

The computing system 402 further includes a data store 404 which mayinclude account data 406. The account data 406 may include one or moreaccounts each associated with identification information of differentusers. For instance, a first account can be associated with a first userwhile a second account can be associated with a second user. Asillustrated in FIG. 4, two or more of the accounts can have aparent-child link therebetween. The account data 406 can include aplurality of different linked accounts.

The computing system 402 yet further includes a processor 414 and memory416 that includes computer-executable instructions that are executed bythe processor 414. In an example, the processor 414 can be or include agraphics processing unit (GPU), a plurality of GPUs, a centralprocessing unit (CPU), a plurality of CPUs, an application-specificintegrated circuit (ASIC), a microcontroller, or the like.

The memory 416 includes an account lookup system 418 configured toreceive a request for a trip of a passenger in an autonomous vehicle100. The request can include identification information associated withthe passenger. The account lookup system 418 can determine whether anaccount associated with the identification information of the passengerincludes a parent-child link. Responsive to detecting a parent-childlink, the account lookup system 418 can further be configured todetermine whether the child passenger is authorized to take the trip inthe autonomous vehicle 100.

The account lookup system 418 can include an authorization component 420and/or a location component 422. The authorization component 420 can beconfigured to determine whether a request for a trip of the child in anautonomous vehicle 100 is authorized based on the parameters and/orrestrictions in the child account 410 that are defined by the parentprior to receipt of the request. For instance, the authorizationcomponent 420 can determine whether the party is authorized to make therequest and/or whether sufficient funds are available for the trip. Inan illustrative example, the authorization component 420 can beconfigured to compare the party requesting the trip with approvedparties, such as the parent, the child, and/or a third party (e.g., Boysand Girls Club) authorized by the parent prior to receipt of therequest. In another illustrative example, the authorization component420 can be configured to calculate a cost of the trip and to determinewhether the child account 410 includes sufficient funds for the trip. Ina yet further illustrative example, the authorization component 420 canbe configured to determine whether the child is requesting a trip duringan authorized time. Where the request is made outside of an authorizedtime period, the authorization component 420 can cause a display toinform the child that the request cannot be completed.

The location component 422 can be configured to determine whether thechild account 410 includes a predefined location that is defined by theparent via the parent-child link. Responsive to detecting a predefinedlocation, the location component 422 can be further configured totransmit the predefined location to the autonomous vehicle 100. Thelocation component 422 can perform the determination responsive toreceiving an indication from the authorization component 420 that therequest is authorized or may be performed independently.

Turning to FIG. 4, the linked account feature can comprise setting apredefined location in the child account 410 as a pickup location for atrip of the child in the autonomous vehicle 100. Conventionally, arequest for a ride of a passenger in an autonomous vehicle 100 willinclude an indication of a pick-up location where the passenger canenter the autonomous vehicle 100. In contrast, responsive to receivingan indication of a parent-child link and one or more predefinedlocations from the location component 422, the disclosed linked accountsystem 120 will automatically set a predefined location in the childaccount 410 as the pickup location. The linked account system 120 caninclude a pickup component 400 configured to receive an indication ofthe one or more predefined locations from the location component 422 andto set a predefined location as a pickup location for a trip of thechild passenger in the autonomous vehicle 100.

The linked account feature can comprise setting a predefined location inthe child account 410 as a destination for a trip of the child in theautonomous vehicle 100. Conventionally, a request for a ride of apassenger in an autonomous vehicle 100 will include an indication of adestination. In contrast, responsive to receiving an indication of aparent-child link and one or more predefined locations from the locationcomponent 422, the disclosed linked account system 120 can automaticallyset a predefined location in the child account 410 as the destinationfor the child passenger (e.g., without the request for the ridespecifying the destination). The parent can indicate a plurality ofpredefined locations in their child's account. Each of the plurality ofpredefined locations can be associated with one or more time periods,such as 2 p.m. Eastern Standard Time (EST) to 3 p.m. EST, Monday andTuesday 1 p.m. EST to 4 p.m. EST, and/or Wednesday, Jan. 9, 2019. Thetime period can indicate a time during which the linked account system120 should set the predefined location as the destination for the tripof the child passenger.

As illustrated in FIG. 5, the linked account system 120 can include adestination component 500. In an embodiment, the destination component500 can receive from the location component 422 an indication of one ormore predefined locations in the child account 410. The destinationcomponent 500 can then select one of the predefined locations to be setas a destination for the trip of the child passenger in the autonomousvehicle 100. The destination component 500 can be configured to selectthe predefined location based on an anticipated time the child passengerwould reach the predefined location. In another embodiment, thedestination component 500 can be configured to limit the destination(s)a child passenger can select when requesting a ride. More specifically,when the child passenger requests a trip in the autonomous vehicle 100,the destination component 500 can present to the child passenger one ormore of the predefined locations in the child account 410. The childpassenger can then select one of the predefined locations to set as thedestination for the trip. Thus, a parent can limit what destination achild passenger can select when they request a trip in the autonomousvehicle 100 s.

Turning now to FIG. 6, the parent-child link can further indicate acontact party in case of a support situation while the child passengeris riding in the autonomous vehicle 100. The linked account feature cancomprise placing the child passenger in communication with their parentwhen a support situation occurs. For instance, the autonomous vehicle100 can automatically place the child in contact with their parent in anemergency. In another embodiment, the autonomous vehicle 100 can placethe child passenger in contact with a support agent (e.g., a person whoprovides support to the passenger) who would then use informationindicated by the parent-child link to put the child in contact withtheir parent. In one embodiment the child passenger can be placed incontact with a support agent. In another embodiment, the child passengercan be placed in contact with a digital assistant (in addition to orinstead of the support agent). The child can then communicate with theirparent or the support agent vocally, textually, and/or the like. Thesupport situation can comprise the sensor system in the autonomousvehicle 100 detecting a predefined support event, the child passengerindicating a request for support, and/or any suitable system fordetecting a passenger's need for support.

As illustrated in FIG. 6, the linked account system 120 can include acommunication component 600 configured to establish a communicationchannel between the child passenger and a mobile computing device 608operated by the parent and/or a support agent to exchange communicationdata. The mobile computing device 608 has an application installed on itthat allows for the application and the communication component 600 toestablish the communication channel. The communication component 600 maybe further configured to receive messages transmitted from the mobilecomputing device 608 via the communication channel. The communicationchannel can be vocal, textual, and/or the like.

For instance, as illustrated in FIG. 6, the autonomous vehicle 100 caninclude a vocal communication system 602 that may be configured for useby a passenger of the autonomous vehicle 100. The communication system602 includes a microphone 604 configured to receive audio data,including speech input from the passenger. The speech input from thepassenger can include any vocal sound made by the passenger, such aswords, phrases, a groan, etc. The communication system 602 furtherincludes a speaker 606 configured to emit sound. The speaker 606 can belocated in any position in the autonomous vehicle 100 suitable for thesound reaching the passenger. For example, the communication system 602can comprise a network of speaker 606 s located around an interior ofthe autonomous vehicle 100. Responsive to detection of a supportsituation, the communication component 600 can establish a vocalcommunication channel with a parent of the child indicated by theparent-child link. In an embodiment, the vocal communication channel canbe established between the autonomous vehicle 100 and the parentindicated by the parent-child link automatically responsive to detectinga support situation. In another embodiment, the vocal communicationchannel is established between the autonomous vehicle 100 and supportpersonnel. The support personnel can then establish a vocalcommunication channel between the autonomous vehicle 100 and the parentindicated by the parent-child link.

In another example, a textual communication channel is establishedbetween the autonomous vehicle 100 and the parent indicated by theparent-child link. The child passenger may use a user interface device(FIG. 2) in the autonomous vehicle 100 to communicate with the parenttextually.

The support personnel can additionally place the parent in contact withthe child passenger via one or more of the communication devicesdescribed above after verifying the existence of a parent-child link.For instance, a parent can contact support personnel and request to beplaced in contact with a child passenger of an autonomous vehicle 100.The support personnel can then verify a parent-child link in accountscorresponding to the parent and the child passenger. Responsive to theverification, the support personnel can cause the communicationcomponent 600 to establish a communication channel between theautonomous vehicle 100 and the parent.

Turning now to FIG. 7, the parent-child link can further cause certainautonomous vehicle information to be presented to the parent by way of adisplay 706 on the parent's mobile computing device 704 before, during,and/or after a trip in the autonomous vehicle 100 when the child is apassenger during the trip. The same information can be presented to theparent when the parent is an additional passenger during the trip or asecond set of autonomous vehicle information can be presented to theparent. By comparison, when the parent is a passenger in the autonomousvehicle 100 without the child, a third set, if any, of autonomousvehicle information can be presented to the parent.

The autonomous vehicle information can include autonomous vehicle 100specifications, geolocation of the autonomous vehicle 100, a view of theinterior cabin of the autonomous vehicle 100, a view of the exterior ofthe autonomous vehicle 100, and/or the like. In an embodiment, theparent can indicate, via the parent-child link, a preference for certainautonomous vehicle information. In another embodiment, defaultautonomous vehicle information can be presented to the parent.

In an embodiment illustrated in FIG. 7, the computing system 402 can bein communication with both a mobile computing device 704 and theautonomous vehicle 100. More specifically, the transceiver 412 of thecomputing system 402 can send data to and/or receive data from both theautonomous vehicle 100 and the mobile computing. The mobile computingdevice 704 can similarly include a transceiver 708 configured totransmit data from the mobile computing device 704 and/or receive dataat the mobile computing device 704. Thus, the mobile computing device704 can be in communication with the computing system 402. The mobilecomputing can further include a display, whereupon graphical featuresmay be presented. For instance, a graphical user interface (GUI) may bepresented as part of the graphical features.

The account lookup system 418 of the computing device can furtherinclude a trip information component 702 configured to cause the displayof the mobile computing device 704 to present the autonomous vehicleinformation. The trip information component 702 can be furtherconfigured to select which mobile computing device 704 will display theautonomous vehicle information. In an embodiment, the trip informationcomponent 702 can select a mobile computing device 704 associated withan account of the parent to display the autonomous vehicle information.In another embodiment, the trip information component 702 can selectboth the mobile computing device 704 associated with the account of theparent and a mobile computing device 704 associated with an account ofan authorized third party (described above) to display some or all thetrip information. For instance, the parent can indicate that the mobilecomputing device 704 of the authorized third party can display a currentlocation of the autonomous vehicle 100 during the trip of the childpassenger.

The linked account system 120 of the autonomous vehicle 100 can furtherinclude a monitor component 700. Responsive to receiving an indicationof the parent-child link, the monitor component 700 can transmit data tothe computing system 402 which can then be formulated for display by themobile computing device 704. For instance, the data can include acurrent geolocation of the autonomous vehicle 100, anticipated time ofarrival at the pickup location and/or drop-off location, license plateof the autonomous vehicle 100, make and/or model of the autonomousvehicle 100, and/or the like. The data can also indicate cleaningprocedures used for airborne allergens and/or presence of detectableairborne allergens within a cabin of the autonomous vehicle 100. Thedata can yet further include pictorial and/or video data from thein-cabin camera 310 regarding the interior cabin of the autonomousvehicle 100. The data can even further include pictorial and/or videodata from the sensor systems 102 and 104 regarding an exterior of theautonomous vehicle 100 before, during, and/or after the trip of thechild passenger.

The trip information component 702 can then synthesize this data andcause the display of the mobile computing device 704 to displayautonomous vehicle information. The trip information component 702 canbe further configured to cause the display of the mobile computingdevice 704 to present one or more alerts before, during, and/or afterthe trip of the child passenger. The alerts can be configured to informthe parent of potentially noteworthy events. For instance, the parentcan receive an alert when the autonomous vehicle 100 is near the pickuplocation and/or drop-off location, when the child passenger entersand/or exits the autonomous vehicle 100, when the autonomous vehicle 100experiences a traffic delay during the trip, and/or the like.

FIG. 8 illustrates an exemplary methodology relating to controlling anautonomous vehicle based on a parent-child link for a child. While themethodology is shown as being a series of acts that are performed in asequence, it is to be understood and appreciated that the methodology isnot limited by the order of the sequence. For example, some acts canoccur in a different order than what is described herein. In addition,an act can occur concurrently with another act. Further, in someinstances, not all acts may be required to implement a methodologydescribed herein.

Moreover, the acts described herein may be computer-executableinstructions that can be implemented by one or more processors and/orstored on a computer-readable medium or media. The computer-executableinstructions can include a routine, a sub-routine, programs, a thread ofexecution, and/or the like. Still further, results of acts of themethodologies can be stored in a computer-readable medium displayed on adisplay device, and/or the like.

Referring now to FIG. 8 an exemplary methodology 800 is illustrated. Themethodology 800 starts at 802, and at 804, a processor receives arequest for a trip of a passenger in an autonomous vehicle. The requestcan include identification information specifying an identity of thepassenger. At 806, the processor determines whether an accountcorresponding to the identification information of the passengerincludes a predefined parent-child link with a second account. Thepredefined parent-child link can indicate a parent-child relationshipbetween the passenger and a party associated with the second account.The parent-child link is defined in the account corresponding to thepassenger maintained by a computing system prior to receipt of therequest for the trip of the passenger in the autonomous vehicle. At 808,responsive to detecting the parent-child link and the passengercomprising the child in the parent-child relationship the processorcauses the autonomous vehicle to enable a linked account feature basedon the parent-child link in the account of the passenger. The linkedaccount feature is disabled in the absence of the parent-child link. Themethodology 800 concludes at 810.

In an embodiment of the methodology 800, responsive to detecting theparent-child link and the passenger comprising the child in theparent-child relationship, the processor further causes a display ofmobile computing device operated by the parent in the parent-childrelationship to display safety information regarding the child passengerriding in the autonomous vehicle. The safety information can include aguide for securing the child passenger in the autonomous vehicle.

In another embodiment of the methodology 800, responsive to detectingthe predefined parent-child link, the passenger comprising the child inthe parent-child relationship, and the parent in the parent-childrelationship being a second passenger for the trip of the autonomousvehicle, causing the autonomous vehicle to enable a second linkedaccount feature, wherein the second linked account feature is differentfrom the linked account feature. The second linked account feature isdisabled in the absence of the parent-child link and the parent and thechild riding together.

Referring now to FIG. 9, a high-level illustration of an exemplarycomputing device that can be used in accordance with the systems andmethodologies disclosed herein is illustrated. For instance, thecomputing device 900 may be or include the mobile computing device orthe computing system. The computing device 900 includes at least oneprocessor 902 that executes instructions that are stored in a memory904. The instructions may be, for instance, instructions forimplementing functionality described as being carried out by one or morecomponents discussed above or instructions for implementing one or moremethods described above. The processor 902 may be a GPU, a plurality ofGPUs, a CPU, a plurality of CPUs, a multi-core processor, etc. Theprocessor 902 may access the memory 904 by way of a system bus 906. Inaddition to storing executable instructions, the memory 904 may alsostore geolocation coordinates of suggested locations or landmarks,roadways, user identification, user preferences, etc.

The computing device 900 additionally includes a data store 910 that isaccessible by the processor 902 by way of the system bus 906. The datastore 910 may include executable instructions, geolocation coordinatesof suggested locations or landmarks, roadways, user identification, userpreferences, etc. The computing device 900 also includes an inputinterface 908 that allows external devices to communicate with thecomputing device 900. For instance, the input interface 908 may be usedto receive instructions from an external computer device, from a user,etc. The computing device 900 also includes an output interface 912 thatinterfaces the computing device 900 with one or more external devices.For example, the computing device 900 may display text, images, etc. byway of the output interface 912.

Additionally, while illustrated as a single system, it is to beunderstood that the computing device 900 may be a distributed system.Thus, for instance, several devices may be in communication by way of anetwork connection and may collectively perform tasks described as beingperformed by the computing device 900.

Various functions described herein can be implemented in hardware,software, or any combination thereof. If implemented in software, thefunctions can be stored on or transmitted over as one or moreinstructions or code on a computer-readable medium. Computer-readablemedia includes computer-readable storage media. A computer-readablestorage media can be any available storage media that can be accessed bya computer. By way of example, and not limitation, suchcomputer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM orother optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium that can be used to store desiredprogram code in the form of instructions or data structures and that canbe accessed by a computer. Disk and disc, as used herein, includecompact disc (CD), laser disc, optical disc, digital versatile disc(DVD), floppy disk, and blu-ray disc (BD), where disks usually reproducedata magnetically and discs usually reproduce data optically withlasers. Further, a propagated signal is not included within the scope ofcomputer-readable storage media. Computer-readable media also includescommunication media including any medium that facilitates transfer of acomputer program from one place to another. A connection, for instance,can be a communication medium. For example, if the software istransmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, DSL, orwireless technologies such as infrared, radio, and microwave areincluded in the definition of communication medium. Combinations of theabove should also be included within the scope of computer-readablemedia.

Alternatively, or in addition, the functionally described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Application-specific Integrated Circuits (ASICs),Application-specific Standard Products (ASSPs), System-on-a-chip systems(SOCs), Complex Programmable Logic Devices (CPLDs), etc.

What has been described above includes examples of one or moreembodiments. It is, of course, not possible to describe everyconceivable modification and alteration of the above devices ormethodologies for purposes of describing the aforementioned aspects, butone of ordinary skill in the art can recognize that many furthermodifications and permutations of various aspects are possible.Accordingly, the described aspects are intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims. Furthermore, to the extent that theterm “includes” is used in either the details description or the claims,such term is intended to be inclusive in a manner similar to the term“comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

What is claimed is:
 1. An autonomous vehicle, comprising: at least afirst user interface device and a second user interface device; acomputing system, comprising: a processor; and memory that storescomputer-executable instructions that, when executed by the processor,cause the processor to perform acts comprising: identifying that a firstpassenger of the autonomous vehicle during a trip in the autonomousvehicle is a child; identifying that a second passenger of theautonomous vehicle during the trip in the autonomous vehicle is a parentof the child, wherein a predefined parent-child link exists between anaccount of the parent and an account of the child; detecting locationsof the parent and the child within the autonomous vehicle during thetrip in the autonomous vehicle, wherein the child is detected as beingin a first seat adjacent to the first user interface device within theautonomous vehicle during the trip in the autonomous vehicle and theparent is detected as being in a second seat adjacent to the second userinterface device within the autonomous vehicle during the trip in theautonomous vehicle; and causing the second user interface device todisplay a control interface to the parent, wherein the control interfacecomprises at least one control configured to enable management ofoperation of the autonomous vehicle, and wherein the first userinterface device is inhibited from displaying the control interface tothe child.
 2. The autonomous vehicle of claim 1, wherein the at leastone control of the control interface comprises one or more of a tripstart control, a trip end control, a door lock and unlock control, or asupport request control.
 3. The autonomous vehicle of claim 1, the actsfurther comprising: causing the first user interface device to displaychild content on the first user interface device.
 4. The autonomousvehicle of claim 3, wherein the child content is selected based oncharacteristics of the child.
 5. The autonomous vehicle of claim 1, theacts further comprising: causing the second user interface device todisplay child-centric specifications of the autonomous vehicle to theparent.
 6. The autonomous vehicle of claim 1, the acts furthercomprising: causing the second user interface to display a guide forsecuring the child in the autonomous vehicle.
 7. The autonomous vehicleof claim 1, further comprising: an in-cabin camera, wherein the in-cabincamera is configured to detect the locations of the parent and the childwithin the autonomous vehicle during the trip in the autonomous vehicle.8. The autonomous vehicle of claim 1, wherein the locations of theparent and the child within the autonomous vehicle are detected based onthe parent entering a code into the second user interface device.
 9. Theautonomous vehicle of claim 1, the acts further comprising: receiving arequest for the trip in the autonomous vehicle for the first passengerand the second passenger, wherein the request includes an indication ofthe predefined parent-child link.
 10. The autonomous vehicle of claim 1,the acts further comprising: receiving a request for the trip in theautonomous vehicle for the first passenger and the second passenger; andresponsive to receiving the request, identifying that the predefinedparent-child link exists between the account of the parent and theaccount of the child.
 11. The autonomous vehicle of claim 1, wherein thepredefined parent-child link sets permissions concerning parameters inthe account of the child that are modifiable by the child.
 12. Acomputing system, comprising: a data store, wherein the data storecomprises a plurality of accounts each associated with differentidentification information; a processor; and memory that storescomputer-executable instructions that, when executed by the processor,cause the processor to perform acts comprising: receiving a request fora trip of a passenger in an autonomous vehicle, wherein the requestincludes identification information specifying an identity of thepassenger; responsive to receiving the request, determining whether apredefined parent-child link exists between an account corresponding tothe identification information of the passenger and a second accountassociated with a second person, wherein the predefined parent-childlink indicates a parent-child relationship between the passenger and thesecond person, wherein the predefined parent-child link is definedbetween the account corresponding to the passenger maintained by thecomputing system and the second account prior to receipt of the requestfor the trip of the passenger in the autonomous vehicle, wherein theaccount corresponding to the identification information of the passengerincludes a predefined location defined in the account maintained by thecomputing system prior to receipt of the request; and responsive todetecting the predefined parent-child link and the passenger comprisingthe child in the parent-child relationship, setting the predefinedlocation as a pick-up location for the trip of the passenger in theautonomous vehicle.
 13. The computing system of claim 12, wherein theaccount corresponding to the identification information for thepassenger includes a plurality of predefined locations defined in theaccount maintained by the computing system prior to receipt of therequest, wherein the predefined location is in the plurality ofpredefined locations, wherein each predefined location of the pluralityof predefined locations is associated with a period of time, wherein theact of setting the predefined location as the pick-up location comprisessetting a selected predefined location from the plurality of predefinedlocations as the pick-up location, wherein the predefined location isselected based on a time of receipt of the request.
 14. The computingsystem of claim 12, wherein the account corresponding to theidentification information for the passenger includes a secondpredefined location, the acts further comprising: responsive todetecting the predefined parent-child link and the passenger comprisingthe child in the parent-child relationship, setting the secondpredefined location as a destination for the trip of the passenger inthe autonomous vehicle.
 15. The computing system of claim 14, whereinthe account corresponding to identification information for thepassenger includes a plurality of predefined locations defined in theaccount maintained by the computing system prior to receipt of therequest, wherein the second predefined location is in the plurality ofpredefined locations, wherein each predefined location of the pluralityof predefined locations is associated with a period of time, wherein theact of setting the second predefined location as the destinationcomprises setting a selected predefined location from the plurality ofpredefined locations as the destination, wherein the predefined locationis selected based on an anticipated time the autonomous vehicle willreach a drop-off location for the trip of the passenger.
 16. Thecomputing system of claim 12, wherein the account corresponding to thepassenger includes an identity of an authorized third party, wherein theauthorized third party is permitted to request a trip for the passengerin the parent-child relationship.
 17. The computing system of claim 16,wherein the account corresponding to the identification information forthe passenger includes a second predefined location associated with theauthorized third party, wherein the act of setting the predefinedlocation as the pick-up location comprises setting the second predefinedlocation as the pick-up location when the request for the trip of thepassenger is provided by the authorized third party.
 18. A methodperformed by a computing system, comprising: receiving a request for atrip of a passenger in an autonomous vehicle, wherein the requestincludes identification information specifying an identity of thepassenger; responsive to receiving the request, determining whether apredefined parent-child link exists between an account corresponding tothe identification information of the passenger and a second accountassociated with a second person, wherein the predefined parent-childlink indicates a parent-child relationship between the passenger and thesecond person, wherein the predefined parent-child link is definedbetween the account corresponding to the passenger maintained by thecomputing system and the second account prior to receipt of the requestfor the trip of the passenger in the autonomous vehicle, wherein theaccount corresponding to the identification information of the passengerincludes a predefined location defined in the account maintained by thecomputing system prior to receipt of the request; and responsive todetecting the predefined parent-child link and the passenger comprisingthe child in the parent-child relationship, setting the predefinedlocation as a destination for the trip of the passenger in theautonomous vehicle.
 19. The method of claim 18, further comprising:responsive to detecting the predefined parent-child link and thepassenger comprising the child in the parent-child relationship, causinga display of a mobile computing device operated by the second person topresent a message indicative of safety information regarding securingthe passenger in the autonomous vehicle, wherein the second personcomprises a parent in the parent-child relationship.
 20. The method ofclaim 18, further comprising: responsive to detecting the predefinedparent-child link and the passenger comprising the child in theparent-child relationship, setting a second predefined location as apick-up location for the trip of the passenger in the autonomousvehicle, wherein the account corresponding to the identificationinformation for the passenger includes the second predefined location.